home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
x2t11.zip
/
ATX2TXT.DOC
< prev
next >
Wrap
Text File
|
1991-09-28
|
9KB
|
172 lines
AtX2Txt - Version: 1.1 - Compiled: 09-28-91 01:10
Convert files with PCBoard's @ variables and colors to text.
══════════════════════════════════════════════════════════════════════════════
┌───────────────────┐
│ ABOUT ATX2TXT ... │
└───────────────────┘
A rather simple program to read files which have been created with
either PCBoard's color codes or @ variables and rewrite them as a simple text
file, ready for viewing by anyone, without PCBoard. The reason for it is my
desire to make bulletins and other files available to my callers while I do
wish to keep using the various codes for on-line display.
The reason for writing this program (as opposed to using one of the
existing ones) is that I could not find one that did all I wanted. With all
that said, let's see what this one will do for you.
AtX2Txt will 1. Use a simple text file where you can list all the files you
wish to process each time;
2. It allows you to specify a new destination file name. The
original is never touched;
3. It allows you to specify an optional ZIP file name to place
the new text file into, presumably for downloading;
4. It will not process files which have not changed since last
processed by AtX2Txt;
5. It will remove all PCBoard @X color codes;
6. It will remove some of the PCBoard @-variables,
specifically, QON, QOFF, MORE, PAUSE, PON, POFF, CLS,
DATAPHONE and HOMEPHONE; More may be added in the future;
7. It will replace some of the PCBoard @-variables,
specifically, SYSTIME, SYSDATE and LASTDATEON will be
replaced by the system time or date of creation of the text
file;
8. There is no limit on the number files which may be processed
nor on the number of ZIP files they are to placed into;
┌────────────────────────┐
│ CAVEAT - READ THIS ... │
└────────────────────────┘
This program is admittedly not for everyone. There are a lot of others
out there which will do similar tasks. AtX2Txt is distributed as FREEWARE,
that is no registration (reads money) is required for it. If it suits your
needs, enjoy. No charges may be imposed by anyone for AtX2Txt of any sort
beyond reasonable reproduction costs.
The program "stamps" all text files created at the end. It records the
date and time the original was last modified (based on the file's date/time).
It also records the program's name, version and where it may be obtained. If
you do not wish this information recorded in the text files created I suggest
you do not use this program. Should a commercial version ever be published
this "stamp" will be optional, of course.
┌─────────────────────────────────┐
│ SETTING UP, GETTING STARTED ... │
└─────────────────────────────────┘
OK, with all that said, let's see how you can set this up quickly to get
started..
You need to create a configuration file, which is a simple text file,
to tell the program what you want it to do. I will use the name ATX2TXT.CFG i
nthis document although the name can be anything you'd like (see command line
options below). Each line in this file represents one task to do and you may
use any number of lines you wish.
Each line is made up of 5 parts which I will call "variables" for lack
of a better term. Variables *MUST* be separated by the vertical bar character
(|) at all times. Their usage, from left to right is as follows:
Variable 1: This is the name of the original file to duplicate, presumably the
one which contains the PCBoard codes. This variable must be a
*complete* file specification for the file to be located. No
searching will be perfomed in order to locate the file; it either
exists as specified or not. This file is opened for read only,
deny none if running on a network.
Variable 2: This is the name of the textfile you wish to create from the above
input file. If the file exists it will be overwritten without
warning! This variable must be a *complete* file specification
for the file to be located. No searching will be perfomed in
order to locate the file for a possible overwrite; it either
exists as specified or not. This file is opened for write only,
deny all if running on a network.
Variable 3: This is an optional variable. If you do not wish to use it
simply type another vertical bar without an entry. If present,
variable 3 specifies the name of the ZIP file within which the
text file (as defined in variable 2) should be placed. This
variable must be a *complete* file specification for the file
to be located. No searching will be perfomed in order to locate
the file; it either exists as specified or not. If it does not
exist, PKZIP will create it for you. This file is not opened by
AtX2Txt, it is used only by PKZIP.EXE. NOTE that if the created
text file is to be placed in a ZIP through this variable it will
be DELETED after PKZIP is finished.
Variable 4: This one is maintained by the program itself to record the last
date your original input file was updated. Whenever you create a
new line in the configuration file be sure to enter six zeros for
this field to assure that the file will be processed with the next
run of the program.
Variable 5: This one is maintained by the program itself to record the last
time your original input file was updated. Whenever you create a
new line in the configuration file be sure to enter six zeros for
this field to assure that the file will be processed with the next
run of the program.
Your configuration file should look something like this:
J:\PCB\BLT60 | G:\TEMP\BLT60.TXT | G:\TEMP\EXECBLTS.ZIP | 910723 | 183204
J:\PCB\BLT61 | G:\TEMP\BLT61.TXT | | 910723 | 183204
J:\PCB\BLT32 | G:\TEMP\INFO.TXT | G:\TEMP\EXECBLTS.ZIP | 000000 | 000000
The spacing is unimportant as is the case the data is typed in. Notice, that
in the above example BLT60 and BLT32 will be ZIPped while BLT61 will not be.
Also, BLT32 is a new addition to the list, so the date and time are entered as
zeros to assure processing.
┌──────────────────────────┐
│ COMMAND LINE OPTIONS ... │
└──────────────────────────┘
Not a lot else to cover here but a few additional notes are in order.
The command line has very few options. You can specify the name of the
configuration file if desired as "ATX2TXT C:MYCONFIG.XXX". If it is not
specified, the program will assume that the name is ATX2TXT.CFG and that it is
located in the CURRENT directory! No searching will be performed for the file.
If you wish to keep the file in a location other than the current one (when the
program runs) you must specify this on the command line, including drive,
directory and file name!
There are only 2 additional command line options available. You can
specify "/I" to ignore file dating. If this option is used it must be the last
item on the command line (in other words, it must follow the configuration name
if that is to be specified). With this switch, the program will process ALL
files listed in the configuration, regardless of their last update.
The "/REGISTER" option is reserved for beta testers only.
┌─────────────────┐
│ THE DISPLAY ... │
└─────────────────┘
The display will show you the progress of of the program. Since I get
rather frustrated watching a program with no screen activity (do you ever
wonder if the sucker is hung?) whenever a file is being processed there is a
"wheel" spinning on the right side of the line.
If the file contained recognized @ variables, a red diamond will show
up immediately preceeding the file specification.
Only the last six lines will be displayed at any given time.
┌──────────────────────┐
│ REVISION HISTORY ... │
└──────────────────────┘
Version 1.0 - Not released, internal use only.
Version 1.1 - September 28, 1991 - 01:10
First official release of the program.